Configuration guide editor to generate interactive configuration guides and automation content

ABSTRACT

Implementations of the present disclosure include methods, systems, and computer-readable storage mediums for receiving the configuration model from a configuration definition repository, the configuration model providing one or more configuration definitions for configuring a software product within a landscape, receiving a landscape plan, the landscape plan defining one or more components of a landscape, on which the software product is to be configured, determining that at least one configuration task of a plurality of configuration tasks is to be executed automatically, the plurality of configuration tasks being included in a workflow that is provided based on the one or more configuration definitions, and the landscape plan, and, in response, automatically executing the at least one configuration task using at least a portion of the automation content.

BACKGROUND

Enterprises can provide computer-implemented solutions (e.g.,application-based products and/or services) in multiple types ofdeployments. Example deployments can include on-premise deployments, andcloud-hosted deployments. On-premise deployments can be described asapplications (e.g., computer-executable programs) that are installed,and executed using hardware (e.g., computers, servers) of the customerconsuming the applications. Cloud-hosted deployments can be described asapplications that are installed, and executed using hardware of a cloudservice provider (e.g., a server farm provided by a third-party serviceprovider). In some examples, enterprises can provide hybrid solutionsthat include both on-premise and cloud-hosted deployments. However,hybrid solutions incur integration, and configuration requirements forthe enterprise providing the hybrid solution, and users of the hybridsolution. The integration and configuration processes can be bothresource, and time intensive.

SUMMARY

Implementations of the present disclosure include computer-implementedmethods for providing interactive configuration guides, and automationcontent for configuring software application deployments.

In some implementations, actions include receiving the configurationmodel from a configuration definition repository, the configurationmodel providing one or more configuration definitions for configuring asoftware product within a landscape, receiving a landscape plan, thelandscape plan defining one or more components of a landscape, on whichthe software product is to be configured, determining that at least oneconfiguration task of a plurality of configuration tasks is to beexecuted automatically, the plurality of configuration tasks beingincluded in a workflow that is provided based on the one or moreconfiguration definitions, and the landscape plan, and, in response,automatically executing the at least one configuration task using atleast a portion of the automation content. Other implementations includecorresponding systems, apparatus, and computer programs, configured toperform the actions of the methods, encoded on computer storage devices.

These and other implementations may each optionally include one or moreof the following features: the at least one configuration task isautomatically executed by a configuration execution runtime; theconfiguration execution runtime is remote, and is provided within aconfiguration target, the configuration target being a component of thelandscape; the at least one configuration task is automatically executedby a script; each configuration definition is provided based onannotations to a computer-readable configuration guide, and theautomation content provided from a configuration expert of an enterpriseproviding the software product; the automation content includes one ormore of a condition indicating a configuration task that can be skipped,a condition group, a target definition indicating a component of thelandscape, a role definition indicating a role of a user required toperform a respective configuration task, and an annotation that can beselected for navigating within the landscape; and the configuration isexecuted as at least part of an integration of multiple softwareproducts, at least one software product including an on-premise product,and at least one software product including a cloud-hosted product.

The present disclosure also provides one or more non-transitorycomputer-readable storage media coupled to one or more processors andhaving instructions stored thereon which, when executed by the one ormore processors, cause the one or more processors to perform operationsin accordance with implementations of the methods provided herein.

The present disclosure further provides a system for implementing themethods provided herein. The system includes one or more processors, anda computer-readable storage medium coupled to the one or more processorshaving instructions stored thereon which, when executed by the one ormore processors, cause the one or more processors to perform operationsin accordance with implementations of the methods provided herein.

It is appreciated that methods in accordance with the present disclosuremay include any combination of the aspects and features describedherein. That is, methods in accordance with the present disclosure arenot limited to the combinations of aspects and features specificallydescribed herein, but also include any combination of the aspects andfeatures provided.

The details of one or more implementations of the present disclosure areset forth in the accompanying drawings and the description below. Otherfeatures and advantages of the present disclosure will be apparent fromthe description and drawings, and from the claims.

DESCRIPTION OF DRAWINGS

FIG. 1 depicts an example conceptual architecture in accordance withimplementations of the present disclosure.

FIG. 2 depicts an example architecture in accordance withimplementations of the present disclosure.

FIG. 3 depicts an example process that can be executed in accordancewith implementations of the present disclosure.

FIGS. 4A-4F depict example screenshots in accordance withimplementations of the present disclosure.

FIG. 5 is a schematic illustration of example computer systems that canbe used to execute implementations of the present disclosure.

Like reference symbols in the various drawings indicate like elements.

DETAILED DESCRIPTION

Implementations of the present disclosure include computer-implementedmethods for providing interactive configuration guides, and automationcontent for configuring software application deployments. Moreparticularly, implementations of the present disclosure are directed togenerating interactive configuration guides, and automation contentusing a central metadata model. In accordance with implementations ofthe present disclosure, and as described in further detail herein, acentral location, and a central content model are provided to structureinformation with a semantic data model for enabling automation, andsimplifying consumption. In some implementations, configuration-relatedartifacts (e.g., sequences, tasks, configuration units, configurationcomponents, parameters, technical scopes, user roles) are provided in acentral repository for performing tasks. Example tasks includegenerating standard documentation (e.g., generic documents, specificdocuments), generating manual task descriptions, and semi-automatedcontent, exchanging configuration definitions, configuration plans, andconfiguration execution, and de-coupling exchange of content andexecution in an automation runtime.

To provide further context for implementations of the presentdisclosure, and as introduced above, enterprises can providecomputer-implemented solutions (e.g., application-based products and/orservices) in multiple types of deployments. As used herein, a solutionrefers to one or more computer-executable programs. Example deploymentscan include on-premise, and cloud-hosted deployments. On-premisedeployments can be described as applications (e.g., computer-executableprograms) that are installed, and executed using hardware (e.g.,computers, servers) of the customer consuming the applications.Cloud-hosted deployments can be described as applications that areinstalled, and executed using hardware of a cloud service provider(e.g., a server farm provided by a third-party service provider). Insome examples, enterprises can provide hybrid solutions that includeboth on-premise, and cloud-hosted deployments.

Implementations of the present disclosure are described in furtherdetail herein with reference to an example hybrid solution. It iscontemplated, however, that implementations of the present disclosurecan be realized with any appropriate configuration. The example hybridsolution includes SAP Business Suite 4 SAP HANA (referred to herein asS/4HANA) provided as an on-premise deployment, and SAP Applicationsprovided as cloud-hosted deployments. Both S/4HANA and the SAPApplications are provided by SAP SE of Walldorf, Germany. In general,S/4HANA can be described as a suite of solutions that is built on SAPHANA, SAP's proprietary operational database system, and in-memorycomputing platform. Example SAP Applications include SAP Ariba, SAPHybris, SAP SuccessFactors, and SAP Fieldglass. Implementations of thepresent disclosure are described in further detail herein with referenceto SAP SuccessFactors, as a non-limiting example, which can be describedas a human capital management (HCM) solution, which includes a suite ofproducts (e.g., Employee Central, Employee Central Payroll, EmployeeCentral Service Center).

As also introduced above, a hybrid solution incurs integration, andconfiguration requirements for the enterprise providing the hybridsolution (e.g., provider enterprise), and users (e.g., customerenterprises). This can include, for example, a user being on-boarded tothe hybrid solution. However, the integration and configurationprocesses can be relatively complex, requiring multiplecomputer-implemented integration/configuration tools, and is bothcomputing resource (e.g., processor, memory), and time intensive.

In some examples, a to-be-integrated product (solution) can includeconfiguration definitions, and guidelines provided by the entityproviding the product (e.g., solution owner, developer). For example,Employee Central of SAP SuccessFactors, described above by way ofexample, is a product that can be integrated to a customer system (e.g.,landscape), and includes associated configuration guidelines (e.g.,Employee Central Configuration (JB1), Minimal Setup Guide, etc.). Insome examples, integration includes performing tasks. An example taskincludes creating user credentials (e.g., using a web user interface(UI)).

In further detail, the implementation of an on-premise or a cloud(on-demand) solution requires the execution of several configurationsteps. The configuration steps are typically documented in configurationguides (e.g., official configuration guides for solutions, and internalconfiguration guides for the operation of cloud solutions). Traditionalattempts to automate configuration guides face multiple problems.Example problems include: the author of the configuration guide is notthe person who produces automation content; configuration guides includechapters, paragraphs, and references to other documents, but nomachine-readable structures with semantically defined entities areprovided; with shorter release cycles, the lifecycle of the softwaredoes not fit to the lifecycle of the configuration guides; andautomation experts are typically experts in a specific automationtechnology, and/or automation language.

In view of the foregoing, implementations of the present disclosure aredirected to providing interactive configuration guides, and automationcontent for configuring software application deployments. Moreparticularly, implementations of the present disclosure enable documentauthors (e.g., authors of configuration guides) to enter semanticinformation associated with configuration-related artifacts into acentral repository. Example configuration-related artifacts include,without limitation, sequences, tasks, configuration units, configurationcomponents, parameters, technical scopes, and user roles. In someimplementations, and as described in further detail herein, theinformation stored in the central repository is used to: generatestandard documentation (e.g., knowledge is stored in the centralrepository, and documentation is generated); provide the documentationas generic documentation, and/or specific documentation (e.g., technicalscopes and parameters can be applied to the documentation); providemanual task descriptions, and semi-automated content; perform exchangeof configuration definition, configuration plan (with scoping andparameters), and configuration execution; and provide decoupled exchangeof content and execution within a specific automation runtime.

FIG. 1 depicts an example conceptual architecture 100 in accordance withimplementations of the present disclosure. In FIG. 1, the exampleconceptual architecture 100 includes a content provider view 102, asolution planning view 104, and a solution implementations view 106.

In the depicted example, the content provider view 102 includes amanagement system and cross-product stack editor 108, and aconfiguration definition repository 110. The management system andcross-product stack editor 108 enables a product owner, and/or a productmodeling expert to create, and/or edit product models 112, andcross-product models 114. In some examples, a product model is providedas a data model that includes a data representation of a product (e.g.,SAP SuccessFactors Employee Central Integration (Cloud Solution), SAPBusiness Suite, SAP S/4HANA 750). In some examples, a cross-productmodel is a data model that includes a data representation of anintegration solution for integrating multiple products (e.g., differentproducts on cloud, and/or on-premise, potential landscape options,defining release dependencies between product models). An examplecross-product model can represent integration of SAP SuccessFactorsEmployee Central Integration and SAP Business Suite. The configurationdefinition repository 110 enables a product owner, and/or aconfiguration modeling expert to create, and/or edit integrationsolution models 116, and configuration models 118.

In accordance with implementations of the present disclosure, aconfiguration model provides structural information to a source format,and can include conditions, condition groups, targets, roles, tasks, andtask conditions. In some implementations, the configuration model isused to provide a configuration guideline, and to enable automation (atleast partial automation) of configuration tasks. That is, and asdescribed in further detail herein, a configuration model can be used byone or more tools for automated configuration of solutions, andproviding configuration guides describing tasks to be performed, rolesfor tasks, conditions, and the like.

In the depicted example, the solution planning view 104 includes amaintenance planner 120, and a configuration planner 122. In someexamples, the maintenance planner 120 is used by a customer to produce amaintenance plan 124 based on customer landscape information 126. Ingeneral, the customer landscape information can describe the underlyingtechnical infrastructure, in which a software product (solution) isinstalled, and executes. In some examples, the configuration planner 120is used by the customer to produce a configuration plan andconfiguration content 128 based on customer scoping and technicalconfiguration data 130.

In the depicted example, the solution implementation view 106 includeslifecycle management (LM) and software logistics (SL) tools 132 that canbe used to implement the maintenance plan 124 in managed systems andsolutions 134 based on software archives 136. The solutionimplementation view 106 also includes configuration tools 138 that canuse the configuration plan and configuration content 128 to configurethe managed systems and solutions 124 based on configuration content andconflict resolution content 140.

In some implementations, during a design time (e.g., conceptuallydepicted as the content provider view 102 of FIG. 1), the product owner(e.g., an enterprise that provides the software product) defines theconfiguration scenario, and, working with a configuration modellingexpert, provides the configuration content. In some implementations,this information is combined in a configuration model that is used toprovide a configuration guide, and automation content. In some examples,a configuration guide, and automation content can be provided forrespective automation tools. In some implementations, during planningtime (e.g., conceptually depicted as the solution planning view 104 ofFIG. 1), automation content, documentation, implementation plans,workflow structures, and the like are provided based on theconfiguration model. In some examples, implementation decisions can beconsidered, and can be based on one or more options of the configurationscenario, the chosen landscape, scenario parameters and technicalparameters. In some implementations, during production use (e.g.,conceptually depicted as the solution implementation view 106 of FIG.1), the automation content provided in the planning time, which containsthe implementation-specific scoping and parameters, is used to executeconfiguration. In some examples, the configuration depends on a specificsequence to configure reuse components on the local system, for example,and to configure technical components and connectivity.

With reference to the above-introduced example, Employee Central of SAPSuccessFactors can be provided as an example integration solution to bedeployed in an example deployment model, such as hybrid, described above(e.g., core hybrid). The example integration solution can be deployed inmultiple integration scenarios, each integration scenario implicatingrespective cross-product stacks, and configuration definitions. For theexample of Employee Central, example integration scenarios, andrespective cross-product stacks, and configuration definitions include:

TABLE 1 Example Integrations Scenarios Cross Product ConfigurationIntegration Scenario Stack Definitions SAP ERP is leveraged for EC-SAP1, 7 Payroll/Time Management HCI for EC Mastered Employees Direct 1 ECTime Off/Payroll in SAP HCI 3 SAP ERP Direct 3 EC Payroll Time Sheet/SAP HCI 3 Payroll in SAP ERP Direct 3 Global OM Mastered in EC, SAP HCI2 data needed in ERP for Direct 2 workflows Cost Center mastered in SAPHCI 4 ERP Direct 4

In some implementations, the configuration definitions are design-timeobjects that include manual task documentation (e.g., existingconfiguration guides), as well as the content required for theimplementation (e.g., configuration plan), and/or for generatingautomation content (e.g., workflow, content files, source code) based onthe respective configuration model.

In some implementations, automation relies on the configuration targets,the scoping parameters, the task list and the related task parameters,and task parameter value determinations. To relate documentation andautomation multiple task levels are provided. Example task levelsincludes logical tasks, technical tasks, and configuration entities. Insome examples, a logical task describes a respective task according thedocumentation data model (e.g., related to a task topic within adocumentation management system (DMS)). In some examples, a technicaltask describes the task based on the configuration definition datamodel. In some examples, the configuration entity describes a definedconfiguration task based on a configuration entity definition. Forexample:

TABLE 2 Examples of Task Levels Logical Task Technical TaskConfiguration Entity Enabling Principal Synchronize theSCP_PRINCIPAL_PROPAGATION Propagation for configured trust (Target HTTPSSCP) Configure the subject SCC_PRINCIPAL_PROPAGATION pattern (TargetSCC) Ensure that Principal SCP_PRINCIPAL_PROPAGATION Propagation isenabled in SCP account (Target SCP) Import the SystemABAP_SSL_SERVER_CERT Certificate for principal ABAP_ICM_RESTARTpropagation into the ERP system (Target ERP) Configure the InternetABAP_PROFILE_PARAMETER Communication Manager (Target ERP) Map SCPidentities to ABAP_EXTID_MAPPING ERP user profiles

In the example of Table 2, the principal propagation is anauthentication mechanism that provides a secure way of forwarding theidentity of a cloud user to a system (e.g., an enterprise resourceplanning (ERP) system).

In some implementations, the configuration entities provide for re-use,abstraction, and hiding micro-logic. In some examples, configurationentities are the re-used parts of the configuration definition, anddocument which parameters are required, and what characteristic theparameters have. In some examples, the configuration entities serve asan abstraction layer between configuration content, and applicationprogram interface (API) calls. For example, configuration entitiesprovide descriptions of the required parameters, and theircharacteristics in an API-independent format. In this manner, theconfiguration content is provided in a unified format. Further, theconfiguration entities hide API consumption micro-logic. For example,automation of a robust meaningful configuration task cannot be achievedwith one API call. Typical examples can include: different API callsdepending on the existence of an object; multiple API calls depending onthe granularity of the APIs; and reading all attributes, changing someattributes, updating all attributes.

In some implementations, and as introduced above, a configuration entitydescribes what must be configured, and what parameters are required.This definition can be provided independent from the existence of realautomation features. In some implementations, the configuration contentrelated to a configuration entity describes the parameters, and thecharacteristics of the parameters (e.g., fixed value, calculated valuebased on other parameters, standard parameter). In some implementations,the runtime-specific implementation provides for a specific automationruntime for the configuration task(s), and contains the requiredmicro-logic to execute the automation. In some examples, theimplementation for a configuration entity can be done as close aspossible to the API to avoid distributed micro logic and to enable easyconsumption.

In some examples, a configuration plan (e.g., the configuration plan 128of FIG. 1) corresponds to a configuration, and to the planning of animplementation project with a defined target landscape, and a definedscope and parameter set for the configuration definition. Theconfiguration plan contains the configuration content for allconfiguration entities. In some examples, the configuration executionrelates to a configuration plan, and includes an execution with aspecific tool of the configuration content (e.g., a configuration tool138 of FIG. 1). For example, the tool can perform at least a portion ofthe configuration in an automated way, and/or can manage execution of amanual task. In any, the configuration execution monitors the status ofeach task (e.g., done, open, error), and provides traceability ofchanges (e.g., who has changed what at what time).

Deliverables and responsibility of content for respective entities willnow be described. Example entities include the integration solution, thecross-product stacks, the configuration definitions, the configurationcontent, configuration entity definitions, configuration entity runtime,and APIs.

In some examples, deliverables associated with each integration solutioninclude a definition and structure of the respective integrationsolution. Responsibility for these deliverables lies on the integrationowner, and a scenario expert. In some examples, deliverables associatedwith a cross-product stack include the definition and rules for thecross-product stack editor. Responsibility for these deliverables lieson the integration owner, and a product expert. In some examples,deliverables for the configuration definition include the configurationdefinition itself, and documentation for any related manual tasks.Responsibility for these deliverables lies with the integration owner,and a documentation expert. In some examples, deliverables associatedwith the configuration content include the configuration content itself,which is provided in the configuration definition. Example configurationcontent includes, without limitation, parameter determination rules(e.g., fixed values, calculated values, rule-based values), scopes,parameters, tasks, and declarative content. Responsibility for thesedeliverables lies with the integration owner, and an automation expert.

In some examples, deliverables associated with the configuration entitydefinitions includes logical re-use tasks, and typical re-use patternfor different target platforms, as well as the definition of theabstract configuration entity with the required definition (e.g.,parameter, parameter metadata, operations, documentation).Responsibility for these deliverables lies with the solution/platformprovider, and the automation expert. In some examples, deliverablesassociated with the configuration entity runtime include the targetruntime specified for a respective configuration entity. Responsibilityfor this deliverable lies with the solution/platform provider, and theautomation expert. In some examples, deliverables associated with eachAPI include the API itself, and maintenance thereof. Responsibility forthese deliverables lies with a respective component owner, and a featureexpert.

FIG. 2 depicts an example architecture 200 in accordance withimplementations of the present disclosure. The example architecture 200includes configuration orchestration 202, and software delivery andlogistics 204 for standard product delivery, portions of each beingsplit between a design-time phase, and a planning and execution (P/E)phase (above and below the dashed line, respectively). In the depictedexample, in the design-time phase, the configuration orchestration 202includes a configuration definition module 206, and the softwaredelivery and logistics 204 includes an application and componentdevelopment module 208. The configuration definition module 206 includesa central repository of configuration definitions (i.e., theconfiguration definition repository 110 of FIG. 1). As described herein,the repository stored configuration definitions with a well-definedcontent structure.

In the depicted example, in the planning and execution phase, theconfiguration orchestration 202 includes a landscape tools component210, and a configuration planning and execution service provider 212,and the software delivery and logistics 204 includes one or more firstconfiguration targets 214. The landscape tools component includes amaintenance planner, which provides landscape planning for integrationscenarios with cross-product stack definitions. The configurationplanning and execution service provider 212 includes an executionservice provider 216, a configuration execution runtime 218, whichincludes a workflow engine and automation content), as well asconfiguration data (e.g., definitions, executions, plans) 220. Theexecution service provider 216 generates workflow definitions that canbe processed by the workflow engine to perform configuration executions.The first configuration targets 214 include, for example, solutions thatare to-be-configured without a local automation runtime, and withoutlocal automation content. Instead, the configurations targets 214 areconfigured using the configuration execution runtime 218.

The example architecture 200 also includes one or more secondconfiguration targets 222. The second configuration targets 222 include,for example, solutions that are to-be-configured with a local automationruntime, and with local automation content. For example, the secondconfiguration targets 222 each include a configuration execution runtime224, an automation runtime 226, and automation content 228.

Implementations of the present disclosure provide an exampleconfiguration include integration of SAP SuccessFactors Employee CentralIntegration (Cloud Solution) with SAP S/4 HANA. It is contemplated,however, that implementations of the present disclosure can be realizedin any appropriate integration and configuration scenario.

In some implementations, during the design-time, a configuration guide(e.g., computer-readable document) is enriched and annotated withautomation enablement content. With reference to FIG. 2, a user (e.g.,an agent of an integration/configuration owner) interacts with theconfiguration definition module 206 of the configuration orchestration202 to perform one or more design-time tasks (e.g., inputting content,and providing definitions). In some examples, content includes, whichconfiguration tasks are to be performed, which role is to performrespective configuration tasks, which target is each configuration taskto be performed on, any conditions that are required for a respectiveconfiguration task to be performed, definitions for parameters used in arespective configuration (e.g., which parameters are fixed, reusedbetween different tasks, are specific to a task), and whichscopes/decisions are possible during the configuration.

In some examples, content includes general information regarding each ofthe products to be integrated. Example general information can include,without limitation, a product identifier (e.g.,SAP_CLOUD_EMPLOYEE_CENTRAL_JB1_1711), a description (e.g., EmployeeCentral Integration (JB1)-1711), a state of the product, a version ofthe product, a short text description (e.g., SAP Cloud JB1 1711, anapplication component identifier (e.g., CA-GTF-INT-EC), andconfiguration documentation (e.g., a hyperlink to a computer-readablefile containing the configuration documentation).

In some examples, the content includes conditions, and/or groupconditions. For example, if a condition exists, which would result in aconfiguration task being skipped, that condition is described in thecondition content. As another example, a condition group can define whatis to be decided, and which options are possible. In some examples, thecontent includes a target definition that defines which configurationtasks occur on which targets (i.e., components of the landscape). Insome examples, a role definition defines which roles are required forexecution of the configuration guide (e.g., Logon to the SAP S/4HANAsystem as Administrator; Logon to SAP S/4HANA system as BusinessExpert).

In some examples, the content includes annotations within theconfiguration guide that identifies targets, and enables directnavigation to each target. For example, an annotation can include ahyperlink within the configuration guide to navigate to a target (e.g.,a user selects the hyperlink, and a UI associated with the target opensin a browser). In some examples, annotations can describe the parametersto be used during the configuration. For example, the annotations canprovide information about re-use of a parameter (e.g., user provides avalue for a parameter as a global parameter that is distributed tomultiple tasks using parameter binding.

In some implementations, one or more configuration tasks are simplifiedby provision of product-specific automation report (e.g., an automationreport specific to S/4 HANA). In general, implementations of the presentdisclosure avoid automation of an original configuration guide, throughprovision of a simplified configuration guide. In some examples, a user(e.g., an agent of the software developer) can interact with thesoftware delivery and logistics 204 to simplify configurationrequirements for a particular product, and provide automation conceptsand automation content with the product delivery.

In some implementations, landscape planning is performed based on theconfiguration definition, and the solution definition. For examplelandscape planning is performed using the landscape planning tools 210of FIG. 2. With reference to the example integration, the selection ofthe Employee Central Integration will identify that, for a specificintegration scenario, a specific configuration definition has to beexecuted. Based on the definition of the targets the different productsand installations for a specific customer are identified, and thecustomer is able to select the targets. Based on the product model, anyrequired software changes can be determined (e.g., an upgrade to a newrelease, or support package level is required).

In accordance with implementations of the present disclosure theconfiguration is performed based on the configuration definition, andthe landscape planning. For example, the configuration execution serviceprovider 212 of FIG. 2 performs the configuration based on informationprovided from the configuration definition. In some examples, theexecution service provider 216 generates a workflow based on theconfiguration definition. In some examples, the workflow includesmultiple phases. In an example phase, one or more users of the customer(e.g., the enterprise for which the products are beingintegrated/configured) are assigned to the defined roles (e.g.,administrator, security expert). In another example phase, the targetsare defined, and can be refined (e.g., values from landscape planningare taken as default values, and can be edited). In another examplephase, condition and scoping are conducted. In another example phase,configuration tasks are performed based on a sequence provided from theconfiguration definition.

In some examples, one or more configuration tasks are performed eitherin a remote configuration execution runtime (e.g., the configurationexecution runtime 218 of FIG. 2), or in a local configuration executionruntime (e.g., the configuration execution runtime 224 of FIG. 2). Insome examples, for a given configuration task, input of one or moreparameter values can be selectively requested based on parameterbindings parameter. A configuration task can be performed as a manualworkflow task, or as an automated workflow task. In some examples, ifautomated, the configuration task includes an automation serviceimplementation within the configuration execution runtime (e.g., theconfiguration execution runtime 218 of FIG. 2).

FIG. 3 depicts an example process 300 that can be executed in accordancewith implementations of the present disclosure. In some implementations,the example process 300 may be performed using one or morecomputer-executable programs executed using one or more computingdevices.

A configuration guide is received (302). For example, the configurationguide can be received by the configuration orchestration 202 of FIG. 2.In some examples, the configuration guide is provided as acomputer-readable file, and can be displayed on a display (e.g., in abrowser). In some examples, the configuration guide detailsconfiguration tasks for a software product that is to be deployed andconfigured for a customer (e.g., enterprise). The configuration guide isannotated with automation enablement content (304). For example, and asdescribed in detail herein, during the design-time, the configurationguide is enriched and annotated with automation enablement content,where a user (e.g., an agent of an integration/configuration owner)interacts with the configuration definition module 206 of theconfiguration orchestration 202 to perform one or more design-time tasks(e.g., inputting content, and providing definitions). In some examples,content includes, which configuration tasks are to be performed, whichrole is to perform respective configuration tasks, which target is eachconfiguration task to be performed on, any conditions that are requiredfor a respective configuration task to be performed, definitions forparameters used in a respective configuration (e.g., which parametersare fixed, reused between different tasks, are specific to a task), andwhich scopes/decisions are possible during the configuration.

A model of configuration definitions is provided and is stored (306).For example, and as described herein, a model is provided, whichincludes the configuration definitions, and is subsequently accessed togenerate content for different execution runtimes. In some examples, themodel is stored in the configuration definition repository 206 of theconfiguration orchestration 202. A configuration model and landscapeplan are received (310). For example, the configuration planning andexecution service provider 212 receives a configuration definition, andlandscape plan for a to-be-configured product. In some examples, theconfiguration definition is provided form the configuration definitionrepository. In some examples, the landscape plan is received from one ormore of the landscape planning tools 210.

A configuration workflow is executed (310). For example, the executionservice provider 216 provides a workflow (e.g., multi-phase workflow, asdescribed herein) that can be at least partially performed by one ormore configuration execution runtimes (e.g., the (local) configurationexecution runtime 218, the (remote) configuration execution runtime224). It can be determined whether a next configuration task is anautomated task (312). If the configuration task is not an automatedtask, the task is executed based on user input (314). For example, oneor more UIs can be displayed to a user, through which the user canprovide user input to perform the task. If the configuration task is anautomated task, the task is automatically executed. For example, one ofthe (local) configuration execution runtime 218, the (remote)configuration execution runtime 224 executes the configuration taskbased on the automation content. It is determined whether any additionalconfiguration tasks need be performed (318). If there is at least oneadditional configuration task, the example process 300 loops back. Ifthere are no additional configuration tasks, the configuration iscomplete (320).

FIGS. 4A-4F depict example screenshots in accordance withimplementations of the present disclosure.

FIG. 4A depicts a screenshot 400 of a portion of an exampleconfiguration guide. In the depicted example, the portion of theconfiguration guide is directed to Integration Package Deployment, andthe example task of creating user credentials using a web UI, which ispart of setting up employee integration for Employee Central, introducedabove. In accordance with implementations of the present disclosure, thedepicted configuration guide can be provided from models stored within aconfiguration definition repository (e.g., the configuration definitionrepository 110 of FIG. 1), which provides structured configurationdefinitions (e.g., integration package deployment), and configurationtasks (e.g., creating user credentials). In short, FIG. 4A depicts anexample result of guide creation in accordance with implementations ofthe present disclosure.

FIG. 4B depicts a screenshot 402 of a portion of a configuration contentmanager that can be used to assist in the example task. The depictedexample corresponds to Employee Central, introduced above, andparticularly, to integration of Employee Central. The configurationcontent manager provides relevant information including details,condition groups, conditions, targets, roles, tasks, task conditions,and the like. Further, the configuration content manager includes a linkto original documentation, which enables a user to navigate to a guide(e.g., the configuration guide of FIG. 4A).

FIG. 4C depicts a screenshot 404 of an example condition selection UI.In some examples, the condition selection UI is displayed in response touser selection of the conditions from the screenshot 402 of FIG. 4B. Insome examples, the condition selection UI enables a user to simulate thecondition and scoping phase of the workflow. In some examples, thecondition selection UI provides a view of the existing configurationdefinition with the condition and scoping rules applied. The user canuse the condition selection UI to verify the results of the conditions(e.g., ensure that relevant tasks are provided, that irrelevant taskshave been removed).

FIG. 4D depicts a screenshot 406 of an example targets UI. In someexamples, the targets UI is displayed in response to user selection oftargets from the screenshots 402, or 404 of FIGS. 4A and 4B,respectively. In some examples, the targets UI provides a list oftargets that are relevant to (e.g., impacted by) the integration. In thedepicted example, example targets include an Employee Central (EC)tenant, an ERP system, a SAP cloud integration (SCI) tenant, and a SAPcloud platform (SCP) system.

FIG. 4E depicts a screenshot 408 of an example roles UI. In someexamples, the roles UI is displayed in response to user selection ofroles from the screenshots 402, 404, or 406 of FIGS. 4A, 4B, and 4C,respectively. In some examples, the roles UI provides a list of roles(e.g., types of users, such as administrators, experts) that arerelevant to (e.g., impacted by) the integration (e.g., perform tasksassociated with the integration). FIG. 4F depicts a screenshot 410 of anexample task content UI. In some examples, the task content UI providesa list of tasks that are to-be-performed for the integration, withrespect configuration entity, task content, description, target, androle to perform the task. In some examples, a messaging channel (e.g.,email) is used to communicate tasks, and other information to the userhaving the role associated with the task. For example, a message can besent to the user indicating a task that the user is to perform, andproviding a workflow (e.g., one or more steps) to be completed by theuser to perform the task. In some examples, the message includes linksto components (e.g., tools) that the user can interact with to performat least a portion of the workflow. In some examples, the message canprovide configuration information (e.g., parameters) that the user canprovide as input in performing the workflow.

FIG. 5 depicts a schematic diagram of an example computing system 500.The system 500 may be used to perform the operations described withregard to one or more implementations of the present disclosure. Forexample, the system 500 may be included in any or all of the servercomponents, or other computing device(s), discussed herein. The system500 may include one or more processors 510, one or more memories 520,one or more storage devices 530, and one or more input/output (I/O)devices 540. The components 510, 520, 530, 540 may be interconnectedusing a system bus 550.

The processor 510 may be configured to execute instructions within thesystem 500. The processor 510 may include a single-threaded processor ora multi-threaded processor. The processor 510 may be configured toexecute or otherwise process instructions stored in one or both of thememory 520 or the storage device 530. Execution of the instruction(s)may cause graphical information to be displayed or otherwise presentedvia a user interface on the I/O device 540.

The memory 520 may store information within the system 500. In someimplementations, the memory 520 is a computer-readable medium. In someimplementations, the memory 520 may include one or more volatile memoryunits. In some implementations, the memory 520 may include one or morenon-volatile memory units.

The storage device 530 may be configured to provide mass storage for thesystem 500. In some implementations, the storage device 530 is acomputer-readable medium. The storage device 530 may include a floppydisk device, a hard disk device, an optical disk device, a tape device,or other type of storage device. The I/O device 540 may provide I/Ooperations for the system 500. In some implementations, the I/O device540 may include a keyboard, a pointing device, or other devices for datainput. In some implementations, the I/O device 540 may include outputdevices such as a display unit for displaying graphical user interfacesor other types of user interfaces.

The features described may be implemented in digital electroniccircuitry, or in computer hardware, firmware, software, or incombinations of them. The apparatus may be implemented in a computerprogram product tangibly embodied in an information carrier (e.g., in amachine-readable storage device) for execution by a programmableprocessor; and method steps may be performed by a programmable processorexecuting a program of instructions to perform functions of thedescribed implementations by operating on input data and generatingoutput. The described features may be implemented advantageously in oneor more computer programs that are executable on a programmable systemincluding at least one programmable processor coupled to receive dataand instructions from, and to transmit data and instructions to, a datastorage system, at least one input device, and at least one outputdevice. A computer program is a set of instructions that may be used,directly or indirectly, in a computer to perform a certain activity orbring about a certain result. A computer program may be written in anyform of programming language, including compiled or interpretedlanguages, and it may be deployed in any form, including as astand-alone program or as a module, component, subroutine, or other unitsuitable for use in a computing environment.

Suitable processors for the execution of a program of instructionsinclude, by way of example, both general and special purposemicroprocessors, and the sole processor or one of multiple processors ofany kind of computer. Generally, a processor will receive instructionsand data from a read-only memory or a random access memory or both.Elements of a computer may include a processor for executinginstructions and one or more memories for storing instructions and data.Generally, a computer may also include, or be operatively coupled tocommunicate with, one or more mass storage devices for storing datafiles; such devices include magnetic disks, such as internal hard disksand removable disks; magneto-optical disks; and optical disks. Storagedevices suitable for tangibly embodying computer program instructionsand data include all forms of non-volatile memory, including by way ofexample semiconductor memory devices, such as EPROM, EEPROM, and flashmemory devices; magnetic disks such as internal hard disks and removabledisks; magneto-optical disks; and CD-ROM and DVD-ROM disks. Theprocessor and the memory may be supplemented by, or incorporated in,application-specific integrated circuits (ASICs).

To provide for interaction with a user, the features may be implementedon a computer having a display device such as a cathode ray tube (CRT)or liquid crystal display (LCD) monitor for displaying information tothe user and a keyboard and a pointing device such as a mouse or atrackball by which the user may provide input to the computer.

The features may be implemented in a computer system that includes aback-end component, such as a data server, or that includes a middlewarecomponent, such as an application server or an Internet server, or thatincludes a front-end component, such as a client computer having agraphical user interface or an Internet browser, or any combination ofthem. The components of the system may be connected by any form ormedium of digital data communication such as a communication network.Examples of communication networks include, e.g., a local area network(LAN), a wide area network (WAN), and the computers and networks formingthe Internet.

The computer system may include clients and servers. A client and serverare generally remote from each other and typically interact through anetwork, such as the described one. The relationship of client andserver arises by virtue of computer programs running on the respectivecomputers and having a client-server relationship to each other.

In addition, the logic flows depicted in the figures do not require theparticular order shown, or sequential order, to achieve desirableresults. In addition, other steps may be provided, or steps may beeliminated, from the described flows, and other components may be addedto, or removed from, the described systems. Accordingly, otherimplementations are within the scope of the following claims.

A number of implementations of the present disclosure have beendescribed. Nevertheless, it will be understood that variousmodifications may be made without departing from the spirit and scope ofthe present disclosure. Accordingly, other implementations are withinthe scope of the following claims.

What is claimed is:
 1. A computer-implemented method executed by one ormore processors for providing interactive configuration guides, andautomation content using a configuration model, the method comprising:receiving, by a local configuration execution runtime, the configurationmodel from a configuration definition repository, the configurationmodel providing one or more configuration definitions for configuring asoftware product within a landscape; receiving, by the localconfiguration execution runtime, a landscape plan, the landscape plandefining one or more components of the landscape, on which the softwareproduct is to be configured; and determining, by the local configurationexecution runtime, that at least one configuration task of a pluralityof configuration tasks is to be executed automatically at aconfiguration target, the plurality of configuration tasks beingincluded in a workflow that is provided based on the one or moreconfiguration definitions, and the landscape plan, the at least oneconfiguration task comprising a logical task having one or moretechnical tasks and one or more configuration entities associatedtherewith, the logical task describing the at least one configurationtask according to a documentation data model, a technical task of theone or more technical tasks describing the logical task based on theconfiguration model, and a configuration entity of the one or moreconfiguration entities describing the at least one configuration taskbased on a configuration entity definition, and, in response todetermining that at least one configuration task of a plurality ofconfiguration tasks is to be executed automatically at a configurationtarget: communicating between the local configuration execution runtimeand a remote configuration execution runtime at the configuration targetfor automatic execution of the at least one configuration task based onthe logical task, the technical task, and the configuration entity;automatically executing, by an automation runtime within theconfiguration target, the at least one configuration task using at leasta portion of the automation content.
 2. The method of claim 1, whereinthe configuration target is a component of the landscape.
 3. The methodof claim 1, wherein the at least one configuration task is automaticallyexecuted by a script.
 4. The method of claim 1, wherein eachconfiguration definition is provided based on annotations to acomputer-readable configuration guide, and the automation contentprovided from a configuration expert of an enterprise providing thesoftware product.
 5. The method of claim 4, wherein the automationcontent comprises one or more of a condition indicating a configurationtask that can be skipped, a condition group, a target definitionindicating a component of the landscape, a role definition indicating arole of a user required to perform a respective configuration task, andan annotation that can be selected for navigating within the landscape.6. The method of claim 1, wherein the at least one configuration task isexecuted as at least part of an integration of multiple softwareproducts, at least one software product comprising an on-premiseproduct, and at least one software product comprising a cloud-hostedproduct.
 7. A non-transitory computer-readable storage medium coupled toone or more processors and having instructions stored thereon which,when executed by the one or more processors, cause the one or moreprocessors to perform operations for providing interactive configurationguides, and automation content using a configuration model, theoperations comprising: receiving, by a local configuration executionruntime, the configuration model from a configuration definitionrepository, the configuration model providing one or more configurationdefinitions for configuring a software product within a landscape;receiving, by the local configuration execution runtime, a landscapeplan, the landscape plan defining one or more components of thelandscape, on which the software product is to be configured; anddetermining, by the local configuration execution runtime, that at leastone configuration task of a plurality of configuration tasks is to beexecuted automatically at a configuration target, the plurality ofconfiguration tasks being included in a workflow that is provided basedon the one or more configuration definitions, and the landscape plan,the at least one configuration task comprising a logical task having oneor more technical tasks and one or more configuration entitiesassociated therewith, the logical task describing the at least oneconfiguration task according to a documentation data model, a technicaltask of the one or more technical tasks describing the logical taskbased on the configuration model, and a configuration entity of the oneor more configuration entities describing the at least one configurationtask based on a configuration entity definition, and, in response todetermining that at least one configuration task of a plurality ofconfiguration tasks is to be executed automatically at a configurationtarget: communicating between the local configuration execution runtimeand a remote configuration execution runtime at the configuration targetfor automatic execution of the at least one configuration task based onthe logical task, the technical task, and the configuration entity; andautomatically executing, by an automation runtime within theconfiguration target, the at least one configuration task using at leasta portion of the automation content.
 8. The computer-readable storagemedium of claim 7, wherein the configuration target is a component ofthe landscape.
 9. The computer-readable storage medium of claim 7,wherein the at least one configuration task is automatically executed bya script.
 10. The computer-readable storage medium of claim 7, whereineach configuration definition is provided based on annotations to acomputer-readable configuration guide, and the automation contentprovided from a configuration expert of an enterprise providing thesoftware product.
 11. The computer-readable storage medium of claim 10,wherein the automation content comprises one or more of a conditionindicating a configuration task that can be skipped, a condition group,a target definition indicating a component of the landscape, a roledefinition indicating a role of a user required to perform a respectiveconfiguration task, and an annotation that can be selected fornavigating within the landscape.
 12. The computer-readable storagemedium of claim 7, wherein the at least one configuration task isexecuted as at least part of an integration of multiple softwareproducts, at least one software product comprising an on-premiseproduct, and at least one software product comprising a cloud-hostedproduct.
 13. A system, comprising: a computing device; and acomputer-readable storage device coupled to the computing device andhaving instructions stored thereon which, when executed by the computingdevice, cause the computing device to perform operations for providinginteractive configuration guides, and automation content using aconfiguration model, the operations comprising: receiving, by a localconfiguration execution runtime, the configuration model from aconfiguration definition repository, the configuration model providingone or more configuration definitions for configuring a software productwithin a landscape; receiving, by the local configuration executionruntime, a landscape plan, the landscape plan defining one or morecomponents of the landscape, on which the software product is to beconfigured; and determining, by the local configuration executionruntime, that at least one configuration task of a plurality ofconfiguration tasks is to be executed automatically at a configurationtarget, the plurality of configuration tasks being included in aworkflow that is provided based on the one or more configurationdefinitions, and the landscape plan, the at least one configuration taskcomprising a logical task having one or more technical tasks and one ormore configuration entities associated therewith, the logical taskdescribing the at least one configuration task according to adocumentation data model, a technical task of the one or more technicaltasks describing the logical task based on the configuration model, anda configuration entity of the one or more configuration entitiesdescribing the at least one configuration task based on a configurationentity definition, and, in response to determining that at least oneconfiguration task of a plurality of configuration tasks is to beexecuted automatically at a configuration target: communicating betweenthe local configuration execution runtime and a remote configurationexecution runtime at the configuration target for automatic execution ofthe at least one configuration task based on the logical task, thetechnical task, and the configuration entity; and automaticallyexecuting, by an automation runtime within the configuration target, theat least one configuration task using at least a portion of theautomation content.
 14. The system of claim 13, wherein theconfiguration target is a component of the landscape.
 15. The system ofclaim 13, wherein the at least one configuration task is automaticallyexecuted by a script.
 16. The system of claim 13, wherein eachconfiguration definition is provided based on annotations to acomputer-readable configuration guide, and the automation contentprovided from a configuration expert of an enterprise providing thesoftware product.
 17. The system of claim 16, wherein the automationcontent comprises one or more of a condition indicating a configurationtask that can be skipped, a condition group, a target definitionindicating a component of the landscape, a role definition indicating arole of a user required to perform a respective configuration task, andan annotation that can be selected for navigating within the landscape.